Skip to main content

View Post [edit]

Poster: Hitsmello Date: Jan 3, 2022 8:32am
Forum: forums Subject: Having trouble archiving Twitter pages

I'm been having trouble archiving Twitter pages since December 8, 2021.
A lot of the time, I just get an error message saying "Sorry. Please try again in ~1 min. Crawling this host is paused because they notified us that are overloaded right now."
And even when I don't get that message, I tend to get messages saying "Error! Unknown error for chrome-error://chromewebdata/ (HTTP status=0)." for several of the outlinks (I ALWAYS try to save the outlinks on a Twitter page).

Reply [edit]

Poster: Hitsmello Date: Jul 3, 2023 8:21am
Forum: forums Subject: Having trouble archiving Twitter pages AGAIN

And now something similar has been happening since June 30 or July 1, 2023 (I'm not entirely sure which).

Whenever I try to archive a Twitter profile, it ALWAYS ends up as the 404 Twitter page, but shows up as a blue, not orange, link in the archive history.

And when I check the box for "Archive up to 3,200 most recent Tweets from this Twitter profile", I get "Could not fetch {twitter_handle} Tweets URLs" or "Could not extract twitter handle from [URL]".

I can't even archive individual tweets through the Wayback Machine. (Archive.today DOES work for Twitter profiles and for individual tweets. Although, apparently, sometimes they'd have to be archived through Google Cache - I'm not entirely sure of which cases this has applied to.)

I think this issue may have to do with the fact that around June 29(?) or June 30 (but before the current Wayback archiving problem), ALL Twitter pages accessed by logged-out users would USUALLY redirect to the Twitter homepage; this generally did not apply to the Wayback Machine though.

Reply [edit]

Poster: Astubudustu Date: Feb 27, 2024 5:19am
Forum: forums Subject: Re: Having trouble archiving Twitter pages AGAIN

hi, i've come across the same problem when trying to archive through the wayback machine (either with twitter, FB and instagram), and i suspect that the problem is indeed that the social redirects to a different page (i think it is a login page for FB and some blanck page with just the logo for the other two, so when viewing the snapshot for that link, there is only the social's logo and nothing else).

Have you come up with any solution?
This post was modified by Astubudustu on 2024-02-27 13:19:21

Reply [edit]

Poster: Astubudustu Date: Feb 13, 2024 6:35am
Forum: forums Subject: Re: Having trouble archiving Twitter pages

i've just come across this problem. At the moment Internet Archive keeps archiving a twitter page, but never finishes its work, nor it says what the problem is. It's just stuck in a loop saying it's arhiving, but it doesnt succed

Reply [edit]

Poster: hafniumragnar Date: Feb 23, 2024 6:53am
Forum: forums Subject: Re: Having trouble archiving Twitter pages

Yes, i come across this problem too. Any solution to help? it says i need to wait 2 hours yet it never proceed

Reply [edit]

Poster: Astubudustu Date: Feb 27, 2024 5:02am
Forum: forums Subject: Re: Having trouble archiving Twitter pages

i've found no solutions. anyways it has once randomly succeded archiving a post, but when i got to see it, it was only a black snapshot with the X logo. Same goes for Instagram posts.

i think it is due to the fact that socials (Facebook, twitter, instagram) require to access to your account in order to see the post. But the archiver is a bot and has no account linked, so it must be redirecting to some login blank page and getting stuck there i guess (?).

Btw i'm not an expert and hope that someone more educated could help us, bc at this point any snapshot of these socials might be useless.

Reply [edit]

Poster: Hitsmello Date: Jan 5, 2022 1:30pm
Forum: forums Subject: Re: Having trouble archiving Twitter pages

Most annoyingly, this is still going on after nearly a month. Why?

Reply [edit]

Poster: Hitsmello Date: Jan 18, 2022 1:23pm
Forum: forums Subject: Re: Having trouble archiving Twitter pages

Up until today, I've been able to sort of work around this by archiving pages beginning with
https://www.twitter.com/*
rather than
https://twitter.com/*
and even if that doesn't capture all the tweets on someone's profile, I can always try adding "?s=20" or even "?fee=25" to the end of the URL.